-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support multiple named bibtex files #12
base: master
Are you sure you want to change the base?
Conversation
This is a great idea! I've also seen people group papers by research topic etc. On my website (where i just manually maintain a Markdown list) I now moved to "selected papers" followed by a long list. Of course for the selected papers I don't want year sub-headers. So i wonder how we can make this more flexible and customizable (maybe with a sort of dict of options in the config file?) |
Yeah, you are right. I have added some variables that should do the job. edit: removed template |
Ah, I see what I missed, we need the settings per file. |
In the current state, it allows for such a configuration: PUBLICATIONS_NAVBAR = True
PUBLICATIONS = {
'peer': {
'title': 'Peer Reviewed',
'file': 'content/peer.bib',
'split_link': False,
'highlight': ['Patrick Holthaus'] },
'others': {
'title': 'Others',
'file': 'content/others.bib',
'split': False,
'bottom_link': False,
'highlight': ['Patrick Holthaus'] }
} |
Updated template:
|
I have updated my personal website now. This is actually a live example of the plugin, the template and configuration above: |
the source code for this site can now be found at https://gitlab.com/pholthau/personal-website |
Extending Readme with Jinja-Filter
This reverts commit 01227e0.
I don't know if pull requests are desired or not. My modifications accomplish the following:
Define multiple bib files like this in
pelicanconf.py
:A header will be generated by default, but can be disabled by setting the following:
Also, publications now are sorted by year so that templates can insert headers in between.
For a live example, please see https://robothouse.herts.ac.uk/publications/